I have a JIRA ticket

• branch and/or PR name(s) include(s) JIRA ID
• issue has "Fix version" assigned
• issue "Status" is set to "In review"
• PR labels are selected

Notable changes for users:

• added possibility to filter fetched data
  Example:

Client use url:

  const URL  = .../?filter[or][field1][gt]=10&filter[or][field1][lt]=3&filter[or][field1][_goperator]=or&filter[or][filed2][like]=LHC_%pass&filter[or][filed2][notLike]=LHC_c%  

The url will be parsed by qs in express to:

  const query = {
      "filter": {
          "or": {
              "field1": {
                  "gt": "10",
                  "lt": "3",
                  "_goperator": "or"
              },
              "filed2": {
                  "like": "LHC_%pass",
                  "notLike": "LHC_c%"
              }
      }
} 

query.filter is being passed as an argument to filterToSequelizeWhereClause function
which returns sequelize-compatible where-clause

 const whereClause = {
 [Symbol(or)]: {
   field1: {
     [Symbol(or)]: {
       [Symbol(gt)]: '10',
       [Symbol(lt)]: '3'
     }
   },
   filed2: {
     [Symbol(and)]: {
       [Symbol(like)]: 'LHC_%pass',
       [Symbol(notLike)]: 'LHC_c%'
     }
   }
 }
} 

What is equivalent to sql:

  WHERE (field1 > 10 OR field1 < 3) OR (field2 like 'LHC_%pass' AND field2 NOT LIKE 'LHC_c%') 

##!!! For entity Run filtering with columns runDuration, endTime, startTime is not supported because they are virtual fields, which with sequelize quering is not possible

Notable changes for developers:

• details of previous in docs of mentioned function filterToSequelizeWhereClause
• func validateDTO renamed to validateDtoOrRepondOnFailure
• object STDEntiryDTO renamed to stdDataRequestDTO
• introduced controllerHandlerWrapper for handling all uncaught errors during processing clients requests
• tests